Remove check of class constraints for specialization #1287
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The original code rejects specializing a function/variable of type without class constraints. That restriction seems unecessary.
stylewarning
force-pushed
the
remove-specialization-limitation
branch
from
83dccb7 to
f4e8d25
Compare
stylewarning
approved these changes
Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original code rejects specializing a function/variable of type without class constraints. That restriction seems unecessary. I had talked with @stylewarning about removing this restriciton.
This is necessary to introduce specialization for LispArrays ( shirok@33ccdd9 ), which allows LispArray accessors/mutators to be inlined and omit runtime dispatch.